Blog
Recent Entries
BoxLang 1.0.0 Beta 23 Launched
The latest release of BoxLang, Beta 23, marks a significant step forward in our journey to create the ultimate dynamic language for the JVM. Packed with powerful new features, important bug fixes, and thoughtful optimizations, this update is designed to make your development experience smoother, faster, and more reliable, especially after now starting to take 100s of comments and bug reports from our community.
TestBox Latest Updates and News!
We’re thrilled to have launched the new TestBox website and TestBox 6.0! If you haven’t had a chance to explore yet, visit TestBox to discover updated documentation, powerful resources, and features that make testing more efficient than ever.
Is Your ColdFusion Application Ready for the Future?
In a rapidly evolving digital world, maintaining performance, security, and scalability for ColdFusion applications is more challenging than ever. Whether you're using Lucee or Adobe ColdFusion, legacy systems can become a bottleneck for growth, innovation, and user satisfaction. The need to future-proof your ColdFusion applications has never been more critical.
But where do you start?
The Hidden Costs of an Outdated ColdFusion Application
As you...
Add Your Comment
(6)
Mar 19, 2013 02:18:17 UTC
by Chris Galli
event.getValue('foo','default'); is not returning as I am understanding it should. I am using prc.isWidget = event.getValue('arguments.isWidget','false'); or prc.isWidget = event.getValue('arguments.isWidget',false); But both return false when my arguments.isWidget value is true by using if (arguments.isWidget){prc.isWidget = true;}else{prc.isWidget = false;}; I get the desired behavior. Am I using this incorrectly?
Mar 19, 2013 02:46:43 UTC
by Brad Wood
You're misunderstanding the event.getValue() method. It is not a general purpose method for accessing any variables in the function but instead a special method specifically for getting values from the request collection. If you do event.getValue('arguments.foo') that is looking for a key called "arguments.foo" in the request collection struct, or rc["arguments.foo"] which is obviously not what you want. If you want to deal with values coming into the arguments scope, you want to use the regular functionality of CFML to deal with that such as CFParam, structKeyExists() and the like. Only use the methods in the event object to work with the request collection.
Mar 19, 2013 11:57:01 UTC
by Chris Galli
Thanks. That makes sense now. Something more like param arguments.isWidget = event.getValue('rc.isWidget','false'); pr.isWidegt = arguments.isWidget; should give the arguments scope priority while gracefully delegating to the rc and then to a default value.
Mar 19, 2013 17:27:41 UTC
by Chris Galli
I discovered I do not need to reference the rc in the event.get value. <br><br> param arguments.isWidget = event.getValue('isWidget','false'); <br><br> prc.isWidget = arguments.isWidget;
Mar 19, 2013 18:00:52 UTC
by Brad Wood
Yep, I was going to comment to that effect but you beat me to it. You only have to pass in the exact name of the variable in the rc to the getValue method. Otherwise it would be looking for rc["rc.foo"] which wouldn't exist. Think of it this way: return event.getValue("foobar"); is the exact same as: var rc = event.getCollection(); return rc.foobar;
Mar 19, 2013 18:01:44 UTC
by Brad Wood
Wow, that's annoying that all our line breaks keep getting eaten-- I'm going to put in a ticket for that :)